Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Advance Debugging #5774

Merged
merged 12 commits into from
Jan 1, 2020
Merged

Advance Debugging #5774

merged 12 commits into from
Jan 1, 2020

Conversation

akosyakov
Copy link
Member

@akosyakov akosyakov commented Jul 22, 2019

What it does

Pause on an exception with watch expressions:
Screen Shot 2019-07-24 at 09 45 04

How to test

  • watch expressions: add watch expressions and start debugging, they should be updated as you go

  • exception breakpoints:

    • they are provided by a debug adapter on the first run, so start debugging something
    • after that you can enable them
    • after the debug session is finished, such breakpoints should be preserved anyway and reevaluated on next run
    • when exception breakpoint hits you should be able to see the reason in an editor
  • function breakpoints:

  • inlined breakpoints

    • look out for regressions with usual breakpoints, one should be able to mix them, disable, enable, edit on the same line via the context menu in the ruler and the breakpoints debug view
  • breakpoints identity issues in the plugin host process: TBD

@akosyakov akosyakov added the debug issues that related to debug functionality label Jul 22, 2019
@akosyakov akosyakov force-pushed the ak/advance_debug branch 2 times, most recently from 225056c to 7bae251 Compare July 23, 2019 09:46
@akosyakov akosyakov force-pushed the ak/view_containers_integration branch from 624192b to 3e25344 Compare July 23, 2019 21:30
@akosyakov akosyakov force-pushed the ak/view_containers_integration branch from 3e25344 to 9604944 Compare July 25, 2019 13:02
@akosyakov akosyakov force-pushed the ak/advance_debug branch 4 times, most recently from add7a65 to 5413b27 Compare July 26, 2019 08:12
@akosyakov akosyakov force-pushed the ak/view_containers_integration branch 9 times, most recently from 94c8539 to 80c4e86 Compare August 2, 2019 14:29
@akosyakov akosyakov changed the base branch from ak/view_containers_integration to master August 24, 2019 20:14
@akosyakov akosyakov marked this pull request as ready for review August 27, 2019 07:02
@akosyakov akosyakov requested a review from a team as a code owner August 27, 2019 07:02
@akosyakov akosyakov requested a review from a team August 27, 2019 07:02
@tolusha
Copy link
Contributor

tolusha commented Aug 27, 2019

@akosyakov Is it ready for review?

@akosyakov
Copy link
Member Author

@tolusha I did not have time to add test sample VS Code extension to test identity of breakpoints in the plugin host process, but the rest should be good.

@tolusha
Copy link
Contributor

tolusha commented Dec 11, 2019

@akosyakov
I probably won't be able handle this PR starting next week

@akosyakov
Copy link
Member Author

@tolusha the problem is that we are going to prohibit to hard code colors in css, only css color variables can be used which are first registered via ColorContribution, i.e. all colors should be themable. This PR introduces such hardcoding.

You can change base of this PR to branch of #6722, introduce new colors and update css to use them. So this PR will be prepared for testing after theming PR is merged. Colors should be registered with ids as in VS Code, i.e. with debugExceptionWidget.background and debugExceptionWidget.border. For default values and descriptions please look up VS Code code base. After registration colors can be referenced in css with var(--theia-debugExceptionWidget-background) and var(--theia-debugExceptionWidget-border).

@akosyakov
Copy link
Member Author

I'm going to reset base branch for it as #6722 and add missing colors.

@akosyakov akosyakov changed the base branch from master to color_theming December 26, 2019 11:24
@akosyakov
Copy link
Member Author

I've fixed theming, so it should be fine to merge after the theming PR is in.

@thegecko I think all comments except using the context menu to add inline breakpoints were fixed. Would it be alright to tackle management of inline breakopints via the context menu separately? Right now one can add it by putting a cursor at some position and using the command palette, the debug top-level menu or the short-cut shift + f9.

@tolusha If you are fine with changes please don't forget to give an approve.

@thegecko
Copy link
Member

@akosyakov, perhaps open an issue to add the context menu item? Happy to merge as is.

@akosyakov akosyakov changed the base branch from color_theming to master December 27, 2019 18:59
@akosyakov
Copy link
Member Author

@thegecko I've filed an issue for inline breakpoints management with the context menu: #6795 I'm going to rebase the PR and if the build is green then merge it.

akosyakov and others added 12 commits January 1, 2020 18:37
Signed-off-by: Anton Kosyakov <[email protected]>
- fix #5767 - function breakpoints support
- fix #5788 - preserve breakpoints identity in the plugin host process

Signed-off-by: Anton Kosyakov <[email protected]>
Signed-off-by: Anatoliy Bazko <[email protected]>
Signed-off-by: Anatoliy Bazko <[email protected]>
Signed-off-by: Anatoliy Bazko <[email protected]>
Signed-off-by: Anatoliy Bazko <[email protected]>
@akosyakov akosyakov dismissed thegecko’s stale review January 1, 2020 19:34

changes were addressed: #5774 (comment)

@akosyakov akosyakov merged commit 3b4b1e5 into master Jan 1, 2020
@akosyakov akosyakov deleted the ak/advance_debug branch January 1, 2020 19:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
debug issues that related to debug functionality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants